impala.tests.test_dbapi_connect.ImpalaConnectionTests.test_retry_dml generally fails for me (and failed also before making any modifcations)

I wrote test_retry_dml in a hurry and it is not surprising that it is flaky - practically it relies on Impala's non local catalog's slowness due to statestore's low update frequency. I will try to rework it to be more reliable.

I'm using impala quickstarter (4.4.1) for local test execution, no hive tests executed

Can you give more info on the env? What is exactly impala quickstarter? :)

@paulmayer
Created a PR to make test_retry_dml more reliable by using a Impala debug action to trigger the timeout:
#566
Tested it with legacy and local catalog Impala (on local catalog it was failing before the patch) and checked that allowing retries during ExecuteStatement leads to failing the test.
Can you check if it is green is your environment?